Method and apparatus for inferring state transitions in a wireless communications network

ABSTRACT

A method, a computer readable medium and an apparatus for inferring state transitions in a wireless communications network are disclosed. In one embodiment, the method infers a state promotion procedure. In another embodiment, the method infers a state demotion procedure.

The present disclosure relates generally to communication networks and,more particularly, to a method and apparatus for inferring statetransitions in a wireless communications network, e.g., a cellularnetwork.

BACKGROUND

As usage of wireless communication networks, e.g., 3G (third generation)cellular networks, continues to grow, a customer's ability to access andutilize the network depends on the availability of capacity. In order toefficiently utilize the limited radio resources, the cellular network ismanaged using one or more radio network controllers. For example, theUniversal Mobile Telecommunications System (UMTS), which is among themost popular 3G networks, allocates radio resources via a radio resourcecontrol (RRC) protocol implemented in radio network controllers.

The radio resource allocation to a user endpoint device is determinedbased on the state of the device. Hence, as the device transitions fromone state to another state, the user endpoint device may be allocated adifferent amount of radio resource.

However, different service providers use different models for the statetransition with varied parameters. For example, one service provider mayuse a model for the state transitions with an inactivity timer shorterthan that used by another service provider. The inactivity timer may beused to determine when a radio resource should be released. Hence, animprovement of the state model (state machine design) depends on firstknowing the type of state machine being used.

SUMMARY

In one embodiment, the present disclosure describes a method, a computerreadable medium and an apparatus for inferring state transitions in acellular network. In one embodiment, the method sets a radio resourcecontrol state for a user endpoint device to a first state, wherein thefirst state is associated with a first level of a radio resource, andsends a first number of packets from the user endpoint device to a radionetwork controller, wherein a size of the first number of packets doesnot trigger a promotion from a second state to a third state, whereinthe second state is associated with a second level of the radioresource, wherein the third state is associated with a third level ofthe radio resource, wherein the second level of the radio resource islarger than the first level of the radio resource and the third level ofthe radio resource is larger than the second level of the radioresource. The method receives a first set of echoes associated with thefirst number of packets, and sends a second number of packets from theuser endpoint device to the radio network controller, wherein a size ofthe second number of packets triggers a promotion from the second stateto the third state. The method receives a second set of echoesassociated with the second number of packets, determines a round triptransmission time for sending the second number of packets and receivingthe second set of echoes, and determines if the round trip transmissiontime is larger than a normal round trip transmission time between theuser endpoint device and the radio network controller by a predeterminedlength of time. The method then infers that the promotion procedure is apromotion from the first state to the second state and then to the thirdstate, if the round trip transmission time is larger than the normalround trip transmission time between the user, endpoint device and theradio network controller by the predetermined length of time, and infersthat the promotion procedure is a promotion from the first state to thethird state, if the round trip transmission time is not larger than thenormal round trip transmission time between the user endpoint device andthe radio network controller by the predetermined length of time.

In another embodiment, the method sets a parameter for a number of runsto be performed, and performs a first test and a second test for each ofthe number of runs to be performed, wherein the first test provides afirst round trip transmission time, and the second test provides asecond round trip transmission time. The method determines if adifference between the first round trip transmission time and the secondround trip transmission time is smaller than a predetermined length oftime, and infers that the state demotion procedure is from a third stateto a second state, if the difference between the first round triptransmission time and the second round trip transmission time is smallerthan the predetermined length of time, and infers that the statedemotion procedure is a demotion from the third state to the secondstate followed by a demotion to a first state, if the difference betweenthe first round trip transmission time and the second round triptransmission time is not smaller than the predetermined length of time.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present disclosure can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram depicting an illustrative cellular networkrelated to the current disclosure;

FIG. 2 illustrates a first exemplary RRC state machine implemented in anRNC;

FIG. 3 illustrates a second exemplary RRC state machine implemented inan RNC;

FIG. 4 illustrates a flowchart of a method for inferring a statepromotion procedure of a radio resource controller state machine;

FIG. 5 illustrates a flowchart of a method for inferring a statedemotion procedure of a radio resource controller state machine; and

FIG. 6 illustrates a high-level block diagram of a general-purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

The present disclosure broadly describes a method, a computer readablemedium and an apparatus for providing a dynamic inactivity timer in awireless communications network, e.g., a cellular network. Although thepresent disclosure is described below in the context of a cellularnetwork, the teaching is not so limited. Namely, the teachings of thecurrent disclosure can be applied for other types of networks, whereinresources are allocated based on states and transitions between states.

FIG. 1 is a block diagram depicting an illustrative cellular network 100related to the present disclosure. In one embodiment, the cellularnetwork 100 can be a 3G cellular network, e.g., a universal mobiletelecommunications system (UMTS) network. However, it should be notedthat the cellular network 100 may include other types of cellularnetworks such as general packet radio services (GPRS) networks, globalsystem for mobile communication (GSM) networks, enhanced data rates forGSM evolution (EDGE) networks, Long Term Evolution (LTE) networks, andso on.

In one embodiment, the network 100 includes three subsystems comprising:a user endpoint (UE) device subsystem 110, a UMTS terrestrial radioaccess network (UTRAN) subsystem 120 and a core network (CN) 130.

In one embodiment, the UE subsystem 110 includes one or more userendpoint devices 112. The user endpoint devices 112 may include a mobiletelephone, a smart phone, a messaging device, a tablet computer, alaptop computer, an air card and the like. The user endpoint devices 112may communicate wirelessly with the cellular network 100.

In one embodiment, the UTRAN subsystem 120 includes one or more basestations 122 and 124 and a radio network controller (RNC) 126. The UTRANsubsystem 110 provides connectivity between the user endpoint devices112 and the core network 130. The UTRAN subsystem 120 provides featuressuch as packet scheduling, radio resource control (RRC) and handovercontrol via the RNC 126.

In one embodiment, the core network 130 includes a serving GPRS supportnode (SGSN) 132, a gateway GPRS support node (GGSN) 134 in communicationwith the Internet 136. The GGSN 134 serves as a gateway hiding UMTSinternal infrastructures from an external network.

The core network 130 serves as the backbone of the cellular network 100.It should be noted that FIG. 1 is a simplified representation of thenetwork 100 and is not intended to illustrate all of the components ofthe network 100. For example, although two base stations 122 and 124 areillustrated, the network 100 may include any number of base stations andso on. Moreover, the cellular network 100 may also include additionalhardware or network components that are not illustrated. In other words,FIG. 1 is an illustration of an exemplary simplified cellular network100.

In one embodiment, the radio resource allocation to the user endpointdevices is handled via a radio resource control (RRC) functionalityimplemented in radio network controllers. For the example in FIG. 1, theRRC functionality is implemented in the RNC 126.

In one embodiment, in the context of UMTS, the radio resource refers tothree factors that are potential bottlenecks of the network: thefrequency spectrum, the WCDMA code space, and the UTRAN transmissionpower. It is important to note that the radio resource usage, deviceenergy consumption and user experiences are all based on the state ofthe user endpoint device. To efficiently utilize the limited radioresources, the RRC protocol introduces a state machine associated witheach user endpoint device. The allocated radio resource for a userendpoint device is then determined based on its state (RRC state).

In order to more clearly illustrate the teachings of the currentdisclosure, the RRC states will first be described. RRC states are usedto allocate radio resources, with each state being associated with adifferent amount (or level) of the resource. For example, if there areonly two states, one state may be associated with allocating zeroresources while the second state may be associated with allocating amaximum resource level. In another example, there may be eleven stateswith each state associated with zero to 100% of a resource level (e.g.,0%, 10%, 20%, . . . , 100%). The RRC states may then be any number ofstates with each state associated with a resource level. In oneembodiment, the resource levels may be assigned according to a serviceprovider's preference.

In one embodiment, the RRC state machine comprises three states used inUMTS cellular networks. The three RRC states are: an IDLE state, aCELL_DCH state and a CELL_FACH state, as described below. It should benoted that the teachings of the current disclosure can be applied inother networks with different RRC state machines. As such, theembodiment as applied and described below for UMTS cellular networks isnot intended to limit the scope or applicability of the currentdisclosure.

In one embodiment, the IDLE state refers to a default state of the userendpoint device when the user endpoint device is turned on. The userendpoint device in the IDLE state has not established an RRC connectionwith the RNC, thus no radio resource is allocated to the user endpointdevice. A user endpoint device in the IDLE state cannot transfer anydata. However, it is allowed to send control messages through a sharedcontrol channel for initializing an RRC connection. A user endpointdevice in the IDLE state consumes little to no energy.

In one embodiment, the CELL_DCH refers to a state wherein the RRCconnection with the RNC is established and the user endpoint device isallocated dedicated transport channels in both downlink (RNC to userendpoint device) and uplink (user endpoint device to RNC) directions.The CELL_DCH state allows the user endpoint device to fully utilize theradio resources for user data transmission. The user endpoint device canaccess the network in HSPA (High Speed Packet Access) mode, if thenetwork infrastructure supports HSPA. CELL_DCH may also be referred toas DCH. A user endpoint device in the CELL_DCH state has the highestamount of energy consumption and the maximum bandwidth.

In one embodiment, CELL_FACH refers to a state wherein the RRCconnection is established with the RNC, but there is no dedicatedchannel allocated to the user endpoint device. Instead, the userendpoint device can only transmit user data through shared low-speedchannels (RACH for the uplink and EACH for the downlink). CELL_FACH mayalso be referred to as FACH. FACH is designed for applications requiringvery low data throughput rate. A user endpoint device in CELL_FACH stateconsumes a lower level of energy and provides a lower level of access,e.g., less than ten Kbps. For example, the energy consumption associatedwith the CELL_DCH may be 50%-100% higher than that associated with theCELL_FACH state.

It is important to note that the RRC state machine is maintained at boththe user endpoint device and the RNC. The two peer entities are alwayssynchronized via control channels except during transient and errorsituations. Also note that both the downlink and the uplink use the samestate machine.

Transitions between the above states (state transitions) are determinedby the user endpoint device's data transmission behavior. As such, theuser endpoint device may be allocated a different amount of radioresource as the user endpoint device transitions from one state toanother state.

In one embodiment, the RRC state machine provides two types of statetransitions: state promotions and state demotions.

State promotions include the state transitions: from IDLE state toCELL_FACH state (IDLE→FACH), from IDLE state to CELL_DCH state(IDLE→DCH), and from CELL_FACH state to CELL_DCH state (FACH→DCH). Thestate transition for a promotion involves switching from a first statewith lower radio resource allocation and lower user endpoint deviceenergy consumption to a second state with more radio resourceconsumption and more user endpoint device energy consumption.

State demotions include the state transitions: from CELL_DCH state toCELL_FACH state (DCH→FACH), from CELL_FACH state to IDLE state(FACH→IDLE), and from CELL_DCH state to IDLE state (DCH→IDLE). The statetransition for a demotion involves switching from a first state withhigher radio resource allocation and higher user endpoint device energyconsumption to a second state with lower (or no) radio resourceconsumption and lower (or no) user endpoint device energy consumption.

Depending on the starting state, a state promotion is triggered byeither any user data (as opposed to control data) transmission activity,if the user endpoint device is at IDLE, or the per-user endpoint devicequeue size (called RLC (Radio Link Controller) buffer size) exceeding athreshold in either the uplink or downlink direction, if the userendpoint device is at CELL_FACH.

In one embodiment, the state demotions are triggered by two inactivitytimers maintained by the RNC. Let, α denote the inactivity timer for thestate demotion DCH→FACH and let β denote the inactivity timer for thestate demotion FACH→IDLE. If the state demotion DCH→IDLE exists, aninactivity timer for the DCH→IDLE may also be defined.

To illustrate the usage of inactivity timers, assume that the inactivitytimer α is set to a predetermined fixed threshold, e.g., T seconds,Whenever the RNC observes any uplink or downlink data frame while theRNC is at the CELL_DCH state, the RNC may then reset the inactivitytimer. If there is no user data transmission activity for T seconds, theinactivity timer times out and the state of the user endpoint device isdemoted to FACH. A similar scheme may be used for the β timer and theinactivity timer associated with the demotion DCH→IDLE, if applicable.

Different service providers may use different models for the statetransitions described above with varied parameters. In one example, oneservice provider may allow transitions from the IDLE state to theCELL_DCH state directly, while another server provider allows transitionfrom the IDLE state only to the CELL_FACH state. In another example, oneservice provider may use a model for the state transitions with one ormore of the inactivity timers being shorter than the inactivity timersused by another service provider. The inactivity timers may be used todetermine when a radio resource should be reallocated. Hence, animprovement of the state model (the state machine design) depends onknowledge of the type of state machine being used.

In one embodiment, the current disclosure provides a method fordetermining state transitions by probing the user endpoint devices andusing an inference technique. The method determines the type of statemachine being used. In order to more clearly illustrate the inferencetechnique, two exemplary RRC state machines will first be described.

FIG. 2 illustrates a first exemplary RRC state machine 200 implementedin an RNC, e.g., the RNC 126. The RRC state machine 200 comprises threestates: an IDLE state 202, a CELL_DCH state 204 and a CELL_FACH state206, in accordance with the descriptions of the various states describedabove.

For example, if the RRC state machine is in the IDLE state 202 and anydata is sent or received, a promotion may occur to the CELL_DCH state204. This is illustrated by line 208. Alternatively, if the RRC statemachine is in the CELL_FACH state 206 and the downlink or uplink queuesize is greater than a predetermined threshold, a promotion may occur tothe CELL_DCH state 204. This is illustrated by line 210.

Similarly, for the demotions, if the RRC state machine is in theCELL_DCH state 204 and the amount of inactivity time exceeds a maximuminactivity time a (or INACTIVITY_(MAX) _(—) _(DCH)) then a demotion mayoccur to the CELL_FACH state 206. This is illustrated by line 212. Forexample, if α is set to 5 seconds and there is no user data transmissionactivity for 5 seconds, the RRC state associated with the user endpointdevice is demoted from the CELL_DCH state 204 to CELL_FACH state 206.Alternatively, if the RRC state machine is in the CELL_FACH state 206and the amount of inactivity time exceeds a maximum inactivity time β,(or INACTIVITY_(MAX) _(—) _(FACH)) then a demotion may occur to the IDLEstate 202. This is illustrated by line 214. For example, if β is set to12 seconds and there is no user data transmission activity for 12seconds, the RRC state associated with the user endpoint device isdemoted from the CELL_FACH 206 state to the IDLE state 202.

FIG. 3 illustrates a second exemplary RRC state machine 300 implementedin an RNC, e.g., the RNC 126. The RRC state machine 300 comprises threestates: an IDLE state 302, a CELL_DCH state 304 and a CELL_FACH state306, in accordance with the descriptions of the various states describedabove.

For example, if the RRC state machine is in the IDLE state 302 and anydata is sent or received, a promotion may occur to the CELL_FACH state306. This is illustrated by line 309. Alternatively, if the RRC statemachine is in the CELL_FACH state 306 and the downlink or uplink queuesize is greater than a predetermined threshold, a promotion may occur tothe CELL_DCH state 304. This is illustrated by line 310.

Similarly, for the demotions, if the RRC state machine is in theCELL_DCH state 304 and the amount of inactivity time exceeds a maximuminactivity time a (or INACTIVITY_(MAX) _(—) _(DCH)) then a demotion mayoccur to the CELL_FACH state 306. This is illustrated by line 312. Forexample, if α is set to 5 seconds and there is no user data transmissionactivity for 5 seconds, the RRC state associated with the user endpointdevice is demoted from the CELL_DCH state 304 to CELL_FACH state 306.Alternatively, if the RRC state machine is in the CELL_FACH state 306and the amount of inactivity time exceeds a maximum inactivity time β,(or INACTIVITY_(MAX) _(—) _(FACH)) then a demotion may occur to the IDLEstate 302. This is illustrated by line 314. For example, if β is set to12 seconds and there is no user data transmission activity for 12seconds, the RRC state associated with the user endpoint device isdemoted from the CELL_FACH 306 state to the IDLE state 302.

It should be noted that the RRC state machines 200 and 300 are onlyexemplary RRC state machines used in a cellular network. The embodimentsof the present disclosure may be equally applicable to other variationsof RRC state machines.

It should be noted that the CELL_DCH inactivity timer and the CELL_FACHinactivity timer may be set to any time period. The specific inactivitytimes are provided only as examples and should not be consideredlimiting.

It should also be noted that state machine promotions and demotionsincrease the management overhead of the RNC and worsen the userexperience. Furthermore, state promotions involve more work (moreprocessing time cycles) than demotions. In particular, state promotionsincur ramp-up latency (e.g., two seconds), during which several controlmessages are exchanged between the user endpoint device and the RNC forresource allocation (e.g., radio bearer reconfiguration and RRCconnection setup). Hence, excessive state promotions and demotionsincrease the management overhead at the RNC and degrade user experience.

One way to reduce the management overhead caused by state machinepromotions and demotions is to increase the values of the inactivitytimers (e.g., α and β). However, increasing the values of the inactivitytimes decreases the radio resource utilization. For example, if the RRCstate machine is in the CELL_DCH and there is no user data transmissionactivity for a time period before the RRC state of the user endpointdevice is demoted to the IDLE state, the resource which was allocated tothe particular user endpoint device remains unused. This effect onutilization may be referred to as tail effect. The tail may be definedas a time period of a constant duration of an inactivity time before astate demotion. The tail time period can never be used to transfer userdata, otherwise the new traffic would have reset the timer and therewould not have been a demotion. Hence, in order to optimize resourceallocations there is a tradeoff among various considerations thatcomprise: radio resource utilization, end user experience, managementoverhead and energy consumption.

As described above, an improvement of the RRC state machine depends onknowledge of the type of state machine being used. The currentdisclosure provides a method for determining the state transitions byprobing the user endpoint devices and using an inference technique, suchthat the above tradeoffs are based on accurate knowledge of the statetransitions. For example, the method may determine a service provideruses an RRC state machine similar to either one of the RRC statemachines illustrated in FIG. 2 or FIG. 3.

In one embodiment, the current method provides a first algorithm ormethod for inferring state promotions and a second algorithm or methodfor inferring state demotions. For clarity, the assumptions for thealgorithms are first provided:

(i) There are at most three states: IDLE, CELL_FACH, and CELL_DCH, andthe CELL_DCH state is the state allowing high data rate transfers;

(ii) The time granularity for inactivity timers is measured in seconds.If the inactivity timers have a finer granularity, a more accurateprobing scheme may be used;

(iii) The state promotion delay is significantly longer than a normalround trip transmission delay for both the CELL_DCH and the CELL_FACHstates; and

(iv) The range of the RLC (Radio Link Controller) buffer thresholds is(64 B-3 KB) for triggering the FACH→DCH promotion.

In one embodiment, the first algorithm for inferring state promotionsdetermines which one of the two promotion procedures used by UMTScellular networks is implemented in the RRC state machine. The twopromotion procedures used for UMTS cellular networks are: P1:IDLE→FACH→DCH and P2: IDLE→DCH. Using the promotion procedure P1:IDLE→FACH→DCH implies that if the RRC state machine is in the IDLE stateand any data is received or sent, the RRC state associated with the userendpoint device is promoted to the CELL_FACH state. A further promotionto the CELL_DCH state occurs if and when the buffer threshold is reachedin accordance with (iv) above. Using the promotion procedure P2:IDLE→DCH implies that if the RRC state machine is in the IDLE state andany data is received or sent, the RRC state associated with the userendpoint device is promoted to the CELL_DCH state directly (withouttransitioning to the CELL_FACH state).

In one embodiment, the first algorithm distinguishes between P1 and P2.In order to distinguish between P1 and P2, the method needs to know whena promotion procedure includes the CELL_FACH state. That is, onepromotion procedure (P2) simply transits from IDLE to CELL_DCHregardless of the number of packets being sent by the user endpointdevice. The second promotion procedure (P1) transits from IDLE to FACHif the user endpoint device sends a small number of packets, and thenproceeds to the CELL_DCH state only if the buffer size exceeds aspecific threshold. Hence, distinguishing between the two types ofpromotion procedures may be performed by sending packets of increasingsizes.

For example, a small number of packets (e.g., overhead only) followed bya large number of packets (e.g., overhead with large content) may besent. If the time to receive a response from the server shows nodifference as the change is made to start sending a large number ofpackets after having sent a small number of packets, the method may theninfer that the promotion procedure is P2. That is, the maximum amount ofresource was already allocated when a small number of packets were beingsent. As such, there is no additional promotion delay to detect.

In contrast, if the time to receive a response from the server shows alarge difference (e.g., 500 ms to an order of 2 seconds) as the changeis made to start sending a large number of packets after having sent asmall number of packets, the method may then infer that the promotionprocedure is P1. That is, the amount of resource allocated when thesmall number of packets was being sent is no longer adequate and thebuffer threshold is being reached. Hence, the server makes a furtherpromotion of the state for endpoint device such that more resources areallocated to the endpoint device. The additional time is detected as thepromotion is occurring from the FACH state to the DCH state.

In the description above, the user endpoint device sends a large numberof packets after sending a small number of packets. The relative terms“small” and “large” are used to signify a number of packets that do nottrigger a promotion from FACH to DCH and a number of packets that dotrigger a promotion from FACH to DCH, respectively. As such, the actualnumber of packets may vary. For convenience, the current method denotesthe RLC buffer size that does not trigger the FACH→DCH promotion by min.The method also denotes the RLC buffer size that triggers the FACH→DCHpromotion by max.

In one embodiment, min is illustratively set to 28 bytes (which is asize that corresponds to an empty UDP packet plus an Internet protocolheader) and max is illustratively set to 3K bytes.

Note that the IDLE→DCH or IDLE→FACH promotion always occurs regardlessof RLC buffer size. That is, if the state of the endpoint device is theIDLE state and the device starts transmitting user data, a promotionoccurs. The promotion is to one of the FACH or DCH states. The algorithmis used in order to detect the presence of an additional promotion.

In one embodiment, the method is implemented in a user endpoint devicewhich utilizes one of the UMTS promotion procedures. The method firstsets (or resets) the RRC state machine for a user endpoint device to theIDLE state. The method then sends min bytes from the user endpointdevice to the RNC. The RNC then sends a response to the endpoint device.The response is referred to as an echo. That is, the RNC echoes minbytes.

In one embodiment, the method then sends max bytes from the userendpoint device to the RNC. The RNC then echoes min bytes. The methodalso records the round trip transmission time for sending the max bytesand receiving the associated echo from the RNC.

In one embodiment, the method then determines if the round triptransmission time recorded above is much larger than normal round triptransmission time. For example, the normal round trip transmission timemay be less than 500 ms while the round trip transmission time forsending the max bytes and receiving the associated echo from the RNC maybe 2.5 seconds. That is, the method determines if the round triptransmission time recorded for sending the max bytes and receiving theassociated echo from the RNC includes an additional promotion delay. Forthe example above, the recorded time includes a promotion delay of twoseconds.

In one embodiment, if the round trip transmission time recorded above ismuch larger than normal round trip transmission time, the method infersthat the promotion procedure P1: IDLE→FACH→DCH is used.

Table 1 provides an exemplary first algorithm for inferring statepromotion. P1 is inferred if the state is promoted to FACH at Step 2 andthen further promoted to DCH at Step 3. That is, P1 is inferred if Δtincludes the additional FACH→DCH promotion delay. Otherwise, the methodinfers that the promotion procedure P2: IDLE→DCH is used. That is, P2 isinferred if Δt does not include the additional promotion delay since thestate is already at DCH after Step 2.

TABLE 1 Exemplary Algorithm for Inferring State Promotion. Algorithm forState Promotion Inference 1: Keep user endpoint (UE) on IDLE 2: UE sendsmin bytes. Server echoes min bytes 3: UE sends max bytes. Server echoesmin bytes. 4: UE records the RTT Δt for Step 3. 5: Report P1 iff Δt >>normal RTT. Otherwise, report P2.

The second algorithm is used for inferring state demotions. The secondalgorithm determines which one of the two demotion procedures used byUMTS cellular networks is implemented in the RRC state machine. The twodemotion procedures used for UMTS cellular networks are: D1: DCH→FACHand D2: DCH→FACH→IDLE. Table 2 provides the algorithm used for inferringwhich demotion procedure is used. The second algorithm identifies thedemotion procedure by performing two types of tests: a first test and asecond test. Both tests are performed for a predetermined number of runsdenoted by n. For example, if the tests are to be performed every secondfor 30 seconds, n is set to 30.

For each run of the first test (i.e., for n=0, . . . 30) the userendpoint device performs the following:

-   -   (i) The user endpoint device sends max bytes to the server in        order to have its RRC state be the CELL_DCH state. The server        echoes min bytes.    -   (ii) The user endpoint device sleeps for n seconds.    -   (iii) The user endpoint device sends min bytes. The server        echoes min bytes.    -   (iv) The user endpoint device records the round trip        transmission time associated with sending the min bytes and        receiving the corresponding echo. The round trip transmission        times for the first test are denoted by Δt₁ (0 . . . 30).

In each run of the first test, the user endpoint device enters theCELL_DCH state by sending max bytes, sleeps for n seconds, and thensends min bytes. By increasing n from 0 seconds to 30 seconds, all thestates experienced by the user endpoint device due to the inactivitytimers are exercised.

The method then performs the second test for n runs. (e.g., for n=0, . .. 30). For each run of the second test the user endpoint device performsthe following:

-   -   (i) The user endpoint device sends max bytes to the server in        order to have its RRC state be the CELL_DCH state. The server        echoes min bytes.    -   (ii) The user endpoint device sleeps for n seconds.    -   (iii) The user endpoint device sends max bytes. The server        echoes min bytes.    -   (iv) The user endpoint device records the round trip        transmission time associated with sending the max bytes in (iii)        and receiving the corresponding echo for the max bytes in (iii).        The round trip transmission times for the second test are        denoted by Δt₂(0 . . . 30).

The second test is similar to the first test, except that after step(iii) of the second test, the user endpoint device is in the DCH state.In contrast, after step (iii) of the first test, if the demotion fromDCH→FACH exists, the user endpoint device is in the FACH state.

The method then compares for each n, Δt₁ (0 . . . 30) and Δt₂(0 . . .30). If the Δt₁ (0 . . . 30) and Δt₂(0 . . . 30) are similar, the methodinfers that the demotion procedure is D1. If the Δt₁ (0 . . . 30) andΔt₂(0 . . . 30) are not similar, the method infers that the demotionprocedure is D2. That is, Δt₁ (0 . . . 30) and Δt₂(0 . . . 30) are notsimilar because the state is demoted to FACH (the α timer), then back toIDLE (the β timer). For convenience Δt₁(•) and Δt₂( ) are use to denoteΔt₁ (0 . . . 30) and Δt₂(0 . . . 30), respectively.

TABLE 2 Exemplary Algorithm for Inferring State Demotion. Algorithm forState Demotion Inference  1: for n = 0 to 30 do  2: UE (user endpoint)sends max bytes. Server echoes min bytes.  3: UE sleeps for n sec.  4:UE sends min bytes. Server echoes min bytes.  5: UE records the RTTΔt₁(i) for step 4.  6: end for  7: for n = 0 to 30 do  8: UE sends maxbytes. Server echoes min bytes.  9: UE sleeps for n sec. 10: UE sendsmax bytes. Server echoes min bytes. 11: UE records the RTT Δt₂(i) forstep 10. 12: end for 13: Report D1 iff Δt₁(•) and Δt₂(•) are similar.Otherwise, report D2

In one embodiment, once the state promotions and demotions are inferred,the method infers other parameters. For example, the inactivity timersmay be directly obtained from the Δt₁(•) and Δt₂(•) computed by thealgorithm for state demotions. Firstly, for the case where the demotionis DCH→FACH→IDLE, one can deduce α and β from the fact that Δt₁ (0 . . .└α+β┘) are smaller than Δt₁(┌α+β┐ . . . 30), and Δt₂(0 . . . └α┘) aresmaller than Δt₂(┌α┐ . . . 30). This is because in the first test of thealgorithm used for inferring demotions, the state promotion IDLE→FACHdoes not happen until n≧┌α+β┐. In the second test, the state promotion(FACH→DCH or IDLE→DCH) happens when n≧┌α┐. Similarly, for the case wherethe demotion is DCH→IDLE, let the only inactivity timer be γ. Then, Δt₁(0 . . . └γ┘) are much smaller than Δt₁(┌γ┐ . . . 30). Then, to inferthe promotion delay X→Y, the round trip time (RTT) including thepromotion is measured. Then, the normal RTT (i.e., not including thepromotion) is subtracted from the result.

In one embodiment, the current method determines the FACH→DCH promotiondelay from the Δt₁ (0 . . . 30) and Δt₂(0 . . . 30) using: └α┘<i≦└α+β┘.

In one embodiment, the current method also infers the RLC bufferthresholds by performing binary search for the packet size that exactlytriggers the FACH→DCH promotion, on each direction. For example, themethod may send packets of increasing size until the FACH→DCH promotionis triggered. The method then identifies the packet size that firsttriggers the FACH→DCH promotion as the RLC buffer threshold.

In order to further illustrate the above method, the state machineinference algorithms described above are used to infer the statepromotions and state demotions for two exemplary service providers(carriers). Each service provider uses one of the UMTS promotion anddemotion procedures.

For each carrier, the algorithms in Tables 1 and 2 are run three times,ensuring that in each experiment:

-   -   (i) the server does not experience a timeout;    -   (ii) no other user data transmission that may trigger other        state transitions is observed; and    -   (iii) the 3G connection is never dropped.

If any of the above conditions are violated, the result is discarded andthe procedure is repeated. Assume then the following results areobserved:

-   -   (i) the normal RTTs for Carriers 1 and 2 are less than 0.3 s;        and    -   (ii) the measured Δt values for the promotion algorithm for        carriers 1 and 2 are (0.2 s, 0.2 s, 0.2 s) and (1.5 s, 1.5 s,        1.5 s), respectively, for the three trials.

Based on the promotion algorithm, the method then infers the promotionprocedures for Carrier 1 and Carrier 2 as being IDLE→DCH andIDLE→FACH→DCH, respectively.

Then, the algorithm used for inferring demotions is run. Suppose, asignificant time difference is observed for Carrier 1 between Δt₁ (5 . .. 16) and Δt₂ (5 . . . 16). The result then indicates that the statedemotion procedure is DCH→FACH→IDLE. Similarly, suppose a significantdisparity exists between Δt₁ (6 . . . 9) and Δt₂ (6 . . . 9) for Carrier2. The result then indicates that Carrier 2 also uses DCH→FACH→IDLE.

Furthermore, suppose that for Carrier 1, Δt₁ (17 . . . 30) and Δt₂ (17 .. . 30) are roughly the same for the demotion algorithm. That means,either sending min bytes or sending max bytes triggers an IDLE→DCHpromotion, implying that it is the only promotion transition for Carrier1.

In contrast, suppose that for Carrier 2, Δt₁ (10 . . . 30) is muchsmaller than Δt₂(10 . . . 30) for the demotion algorithm. Therefore,sending min bytes and sending max bytes in triggering IDLE→FACH andIDLE→DCH, respectively, will result in different promotion delays. Thatmeans, Carrier 2 may perform two types of promotions depending on theRLC buffer size.

The above inferences for Carriers 1 and 2 indicate that Carrier 1 usesan RRC state machine similar to the RRC state machine 200 of FIG. 2, andCarrier 2 uses an RRC state machine similar to the RRC state machine 300of FIG. 3.

Given the Δt₁ (•) and Δt₂(•) values provided above for the demotionalgorithm, α and β may also be inferred. The inference results are(α,β)=(5 s,12 s) for Carrier 1 and (α,β)=(6 s,4 s) for Carrier 2. Toinfer the RLC buffer thresholds triggering FACH→DCH, the experiments maybe repeated several times, e.g., 30 times.

As described above, the radio energy consumption of the user endpointdevice depends on the RRC state of the device. The current method maythen use the variability of the energy consumption to validate theresults of the inference techniques.

For example, in order to confirm the inactivity timers and statepromotion delays, the battery of the UE (e.g., a smartphone) may beattached to a power meter. The power meter may then be connected to acomputer such that the output power of the battery may be recorded.

In one example, after keeping the smartphone in an inactive state for atime period (e.g., 20 seconds), the method may send a UDP packet.Assuming the IDLE→DCH promotion takes approximately 2 sec, the packet issent at about t=23.8 sec. From t=26.1 sec, the phone remains at thehigh-power DCH state for about 5 sec, then switches to the low-powerFACH state at t=31.5 sec. Finally at t=44.1 sec, the phone returns tothe IDLE state. Similar, the FACH→DCH promotion delay for carrier 2'sstate machine may be validated.

By computing the average power using the IDLE power as the baseline, themethod may then derive the energy consumption values. Similarly, themethod may use the energy as an indicator to search for the bufferthreshold that exactly triggers the promotion.

It is important to note that, during probing, all other major systemcomponents that may affect power consumption at the same power state aredisabled to eliminate their effect whenever possible. For example, byclosing all applications and network activities, keeping the screenbrightness at the same level, turning off global positioning systems(GPS) and WiFi, etc., the effect of other components may be reduced.

The above results for Carriers 1 and 2 are summarized in Table 3. Theinferences indicate that Carrier 1 uses an RRC state machine similar tothe RRC state machine 200 and Carrier 2 uses an RRC state machinesimilar to the RRC state machine 300. The carriers have inactivitytimers and RLC buffer thresholds (thresholds triggering FACH→DCH) set todifferent values. Note also that their state transitions from IDLE stateare different. Hence, the carriers may need different optimal statemachine configurations to better balance radio resource utilization andperformance.

TABLE 3 Exemplary inferred parameters for Carriers 1 and 2. Carrier 1Carrier 2 Inactivity timer α: DCH→FACH 5 sec 6 sec β: FACH→IDLE 12 sec 4sec Promotion Time IDLE→FACH N/A 0.6 sec IDLE→DCH 2 sec N/A FACH→DCH 1.5sec 1.3 sec RLC Buffer threshold FACH→DCH (UL) 543 ± 25 B 151 ± 14 BFACH→DCH (DL) 475 ± 23 B 119 ± 17 B State Radio Power DCH 800 mW 600 mWFACH 460 mW 400 mW IDLE 0 0 Promotion Radio Power IDLE→FACH N/A 410 mWIDLE→DCH 550 mW N/A FACH→DCH 700 mW 480 mW

FIG. 4 illustrates a flowchart of a method 400 for inferring a statepromotion procedure of a radio resource controller state machine. In oneembodiment, the method 400 can be implemented in a radio networkcontroller (RNC), a user endpoint device, or a general purpose computerhaving a processor, a memory and input/output devices as discussed belowin reference to FIG. 6. The method 400 starts in step 405 and proceedsto step 410.

In step 410, method 400 sets (or resets) a radio resource control (RRC)state for a user endpoint device to a first state, wherein the firststate is associated with a first level of a radio resource. For example,the first state may be a state in which no radio resource is allocatedto the user endpoint device.

In one embodiment, the first state is an IDLE state, wherein the IDLEstate is a default state of the user endpoint device when the userendpoint device is turned on but the user endpoint device has notestablished a radio resource control connection with the radio networkcontroller.

In step 415, method 400 sends a first number of packets from the userendpoint device to a radio network controller (RNC), wherein the size ofthe first number of packets does not trigger a promotion from a secondstate to a third state, wherein the second state is associated with asecond level of the radio resource, wherein the third state isassociated with a third level of the radio resource, wherein the secondlevel of the radio resource is larger than the first level of the radioresource and the third level of the radio resource is larger than thesecond level of the radio resource.

In one embodiment, the first number of packets is min bytes. In oneembodiment, the second state is the CELL_FACH state and the third stateis the CELL_DCH state. The min bytes then do not trigger a promotionfrom a CELL_FACH state to a CELL_DCH state, even if the promotion fromFACH to DCH exists in the state machine.

In step 420, method 400 receives a first set of echoes associated withthe first number of packets. For example, the method receives from theradio network controller echoes for the min bytes sent in step 415. Forexample, after the radio network controller receives the min bytes, theradio controller sends min bytes to the user endpoint device.

In step 425, method 400 sends a second number of packets from the userendpoint device to the RNC, wherein the size of the second number ofpackets triggers a promotion from the second state to the third state.

In one embodiment, the second number of packets is max bytes. The maxbytes then trigger a promotion from a CELL_FACH state to a CELL_DCHstate, if the FACH to DCH promotion exists in the state machine.

In step 430, method 400 receives a second set of echoes associated withthe second number of packets. For example, after the radio networkcontroller receives the max bytes sent in step 425, it responds to theuser endpoint device with max bytes.

In step 435, method 400 determines a round trip transmission time forsending the second number of packets and receiving the second set ofechoes. For example, the method determines the round trip transmissiontime for sending max bytes and receiving echoes associated with the maxbytes.

In step 440, method 400 determines if the round trip transmission timeis larger than a normal round trip transmission time between the userendpoint device and the radio network controller by a predeterminedlength of time. Generally, a normal round trip transmission timeincludes at least one promotion, since the method is starting from IDLE.However, if an additional promotion delay is included (e.g., a secondpromotion in addition to the first promotion), the round triptransmission time determined above may be on the order of seconds largerthan the normal round trip transmission time. For example, the roundtrip transmission time may be larger than the normal round triptransmission time by 500 ms, 1 sec, 2 sec, etc. If the round triptransmission time is much larger than a normal round trip transmissiontime (i.e., for a single promotion), the method proceeds to step 450.Otherwise, the method proceeds to step 460. In one embodiment, thepredetermined length of time is at least 500 ms.

In step 450, method 400 infers that the promotion procedure is apromotion from the first state to the second state and then to the thirdstate. For example, the promotion procedure may be from the IDLE stateto the CELL_FACH state and then to the CELL_DCH state, as describedabove. That is, the promotion procedure P1: IDLE→FACH→DCH is used. Themethod then either proceeds to step 470 to end processing the currentinference or to step 410.

In step 460, method 400 infers that the promotion procedure is apromotion from the first state to the third state. For example, thepromotion procedure may be from the IDLE state to the CELL_DCH state.That is, the method infers that the promotion procedure P2: IDLE→DCH isused. The method then either proceeds to step 470 to end processing thecurrent inference or to step 410.

FIG. 5 illustrates a flowchart of a method 500 for inferring a statedemotion procedure of a radio resource controller state machine. In oneembodiment, the method 500 can be implemented in a radio networkcontroller (RNC), a user endpoint device, or a general purpose computerhaving a processor, a memory and input/output devices as discussed belowin reference to FIG. 6. The method 500 starts in step 505 and proceedsto step 510.

In step 510, method 500 sets a parameter for a maximum number of runs tobe performed. For example, if the inferring is based on running theinference algorithm every second for 30 seconds, the method sets themaximum number of runs to 30. It should be noted that the value of themaximum number of runs to be performed can be dynamically selected.

In step 515, sets a value of a counter to zero. For example, the methodsets the counter such that it can be used to count the run number from 0to 30, etc.

In step 520, method 500 determines if the value of the counter isgreater than the maximum number of runs. If the value of the counter isgreater than the maximum number of runs, the method proceeds to step575. Otherwise, the method proceeds to step 525.

In step 525, the method then performs a first test, wherein the firsttest comprises:

-   -   (i) sending a first number of packets from a user endpoint        device to a radio network controller (RNC), wherein the size of        the first number of packets triggers a promotion from a second        state to a third state, wherein the second state is associated        with a second level of a radio resource, the third state is        associated with a third level of the radio resource, wherein the        second level of the radio resource is larger than a first level        of the radio resource, and the third level of the radio resource        is larger than the second level of the radio resource, wherein        the first state is associated with a first level of the radio        resource;    -   (ii) receiving a first set of echoes from the RNC associated        with the first number of packets;    -   (iii) the user endpoint device sleeping for a number of seconds        equal to the value of the counter;    -   (iv) sending a second number of packets to the RNC, wherein the        size of the second number of packets does not trigger a        promotion from the second state to the third state;    -   (v) receiving a second set of echoes from the RNC associated        with the second number of packets; and    -   (vi) the user endpoint device determining a first round trip        transmission time for sending the second number of packets and        receiving the second echoes.

In step 550, method 500 performs a second test, wherein the second testcomprises:

-   -   (i) sending a third number of packets to the RNC, wherein the        size of the third number of packets triggers a promotion from        the second state to the third state;    -   (ii) receiving a third set of echoes from the RNC associated        with the third number of packets;    -   (iii) the user endpoint device sleeping for a number of seconds        equal to the value of the counter;    -   (iv) sending a fourth number of packets to the RNC, wherein the        size of the fourth number of packets triggers a promotion from        the second state to the third state;    -   (v) receiving a fourth set of echoes from the RNC associated        with the fourth number of packets; and    -   (vi) the user endpoint device determining a second round trip        transmission time for sending the fourth number of packets and        receiving the fourth echoes.

In one embodiment, the first state is an IDLE state, the second state isa CELL_FACH state, and the third state is a CELL_DCH state. In oneembodiment, the first number of packets is max bytes. In one embodiment,the second number of packets is min bytes. In one embodiment, the thirdnumber of packets is max bytes. In one embodiment, the fourth number ofpackets is max bytes.

In step 555, method 500 increments the value of the counter by one. Themethod then proceeds to step 520.

In step 575, method 500 determines if the difference between the firstround trip transmission time and the second round trip transmission timeis smaller than a predetermined length of time. For example, thedifference may be less than 200 ms, 400 ms or so. If the differencebetween the first round trip transmission time and the second round triptransmission time is less than or equal to the predetermined length oftime, the method proceeds to step 580. Otherwise, the method proceeds tostep 585.

In one embodiment, the predetermined length of time is less than orequal to 500 ms.

In step 580, method 500 infers that the demotion procedure is from thethird state to the second state. For example, the demotion procedure maybe from CELL_DCH to CELL_FACH. For the example described above, thedemotion procedures is D1: DCH→FACH. The method then either proceeds tostep 595 to end processing the current inference or to return to step510.

In step 585, method 500 infers that the demotion procedure is a demotionfrom the third state to the second state followed by a demotion to thefirst state. For example, the method may be a demotion from the CELL_DCHstate to the CELL_FACH state followed by a demotion to an IDLE state.That is, the demotion procedure is D2: DCH→FACH→IDLE. The method theneither proceeds to step 595 to end processing the current inference orto return to step 510.

It should be noted that although not explicitly specified, one or moresteps of the methods described herein may include a storing, displayingand/or outputting step as required for a particular application. Inother words, any data, records, fields, and/or intermediate resultsdiscussed in the methods can be stored, displayed, and/or outputted toanother device as required for a particular application. Furthermore,steps or blocks in FIGS. 4 and 5 that recite a determining operation, orinvolve a decision, do not necessarily require that both branches of thedetermining operation be practiced. In other words, one of the branchesof the determining operation can be deemed as an optional step.

FIG. 6 depicts a high-level block diagram of a general-purpose computerreadable medium suitable for use in performing the functions describedherein. As depicted in FIG. 6, the system 600 comprises a processorelement 602 (e.g., a CPU), a memory 604, e.g., random access memory(RAM) and/or read only memory (ROM), a module 605 for inferring apromotion or a demotion procedure of a radio resource controller statemachine in a network, and various input/output devices 606 (e.g.,storage devices, including but not limited to, a tape drive, a floppydrive, a hard disk drive or a compact disk drive, a receiver, atransmitter, a speaker, a display, a speech synthesizer, an output port,and a user input device (such as a keyboard, a keypad, a mouse, and thelike)).

It should be noted that the present disclosure can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general purposecomputer or any other hardware equivalents. In one embodiment, thepresent module or process 605 inferring a promotion or a demotionprocedure of a radio resource controller state machine in a network canbe loaded into memory 604 and executed by processor 602 to implement thefunctions as discussed above. As such, the present method 605 inferringa promotion or a demotion procedure of a radio resource controller statemachine in a network (including associated data structures) of thepresent disclosure can be stored on a non-transitory computer readablestorage medium, e.g., RAM memory, magnetic or optical drive or disketteand the like.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for inferring a state promotionprocedure of a radio resource controller state machine in a network,comprising: setting, via a processor of a user endpoint device, a radioresource control state for the user endpoint device to a first state,wherein the first state is associated with a first level of a radioresource; sending, via the processor, a first number of packets from theuser endpoint device to a radio network controller, wherein a size ofthe first number of packets does not trigger a promotion from a secondstate to a third state, wherein the second state is associated with asecond level of the radio resource, wherein the third state isassociated with a third level of the radio resource, wherein the secondlevel of the radio resource is larger than the first level of the radioresource and the third level of the radio resource is larger than thesecond level of the radio resource; receiving, via the processor, afirst set of echoes associated with the first number of packets;sending, via the processor, a second number of packets from the userendpoint device to the radio network controller, wherein a size of thesecond number of packets triggers a promotion from the second state tothe third state; receiving, via the processor, a second set of echoesassociated with the second number of packets; determining, via theprocessor, a round trip transmission time for sending the second numberof packets and receiving the second set of echoes; determines, via theprocessor, if the round trip transmission time is larger than a normalround trip transmission time between the user endpoint device and theradio network controller by a predetermined length of time; inferring,via the processor, that the promotion procedure is a promotion from thefirst state to the second state and then to the third state, when theround trip transmission time is larger than the normal round triptransmission time between the user endpoint device and the radio networkcontroller by the predetermined length of time; and inferring, via theprocessor, that the promotion procedure is a promotion from the firststate to the third state, when the round trip transmission time is notlarger than the normal round trip transmission time between the userendpoint device and the radio network controller by the predeterminedlength of time.
 2. The method of claim 1, wherein the first state is anIDLE state.
 3. The method of claim 1, wherein the second state is aCELL_FACH state.
 4. The method of claim 1, wherein the third state is aCELL_DCH state.
 5. The method of claim 1, wherein the first number ofpackets comprises approximately 28 bytes.
 6. The method of claim 1,wherein the second number of packets comprises approximately 3kilobytes.
 7. The method of claim 1, wherein the predetermined length oftime is at least 500 ms.
 8. The method of claim 1, wherein the normalround trip transmission time comprises a single promotion delay of time.9. The method of claim 8, wherein a second delay of time for a second isdetermined from the round trip transmission time and the normal roundtrip transmission time.
 10. A method for inferring a state demotionprocedure of a radio resource controller state machine in a network,comprising: setting, via a processor of a user endpoint device, aparameter for a number of runs to be performed; performing, via theprocessor, a first test and a second test for each of the number of runsto be performed, wherein the first test provides a first round triptransmission time, and the second test provides a second round triptransmission time, determining, via the processor, if a differencebetween the first round trip transmission time and the second round triptransmission time is smaller than a predetermined length of time;inferring, via the processor, that the state demotion procedure is froma third state to a second state, when the difference between the firstround trip transmission time and the second round trip transmission timeis smaller than the predetermined length of time; and inferring, via theprocessor, that the state demotion procedure is a demotion from thethird state to the second state followed by a demotion to a first state,when the difference between the first round trip transmission time andthe second round trip transmission time is not smaller than thepredetermined length of time, wherein each of the first state, thesecond state and the third state is associated with a different level ofa radio resource.
 11. The method of claim 10, wherein the first testcomprises: sending a first number of packets from the user endpointdevice to a radio network controller, wherein a size of the first numberof packets triggers a promotion from the second state to the thirdstate, wherein the second state is associated with a second level of theradio resource, the third state is associated with a third level of theradio resource, wherein the second level of the radio resource is largerthan a first level of the radio resource, and the third level of theradio resource is larger than the second level of the radio resource,wherein the first state is associated with a first level of the radioresource; receiving a first set of echoes from the radio networkcontroller associated with the first number of packets; causing the userendpoint device to sleep for a number of seconds equal to a value of acounter relating to the number of runs to be performed; sending a secondnumber of packets to the radio network controller, wherein a size of thesecond number of packets does not trigger a promotion from the secondstate to the third state; receiving a second set of echoes from theradio network controller associated with the second number of packets;and determining the first round trip transmission time for sending thesecond number of packets and receiving the second set of echoes.
 12. Themethod of claim 11, wherein the second test comprises: sending a thirdnumber of packets to the radio network controller, wherein a size of thethird number of packets triggers a promotion from the second state tothe third state; receiving a third set of echoes from the radio networkcontroller associated with the third number of packets; causing the userendpoint device to sleep for a number of seconds equal to the value ofthe counter; sending a fourth number of packets to the radio networkcontroller, wherein a size of the fourth number of packets triggers apromotion from the second state to the third state; receiving a fourthset of echoes from the radio network controller associated with thefourth number of packets; and determining the second round triptransmission time for sending the fourth number of packets and receivingthe fourth set of echoes.
 13. The method of claim 12, wherein the thirdnumber of packets comprises approximately 3 kilobytes, and wherein thefourth number of packets comprises approximately 3 kilobytes.
 14. Themethod of claim 11, wherein the first number of packets comprisesapproximately 3 kilobytes, and wherein the second number of packetscomprises approximately 28 bytes.
 15. The method of claim 10, whereinthe first state is an IDLE state.
 16. The method of claim 10, whereinthe second state is a CELL₁₃ FACH state.
 17. The method of claim 10,wherein the third state is a CELL_DCH state.
 18. The method of claim 10,wherein the predetermined length of time is less than or equal to 500ms.
 19. The method of claim 10, wherein an inactivity timer for thedemotion from the third state to the second state is determined from thefirst round trip transmission time and the second round triptransmission time.
 20. The method of claim 10, wherein an inactivitytimer for the demotion from the second state to the first state isdetermined from the first round trip transmission time and the secondround trip transmission time.